-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement --force-systemd into cri-o #12553
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spowelljr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
@spowelljr: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
kvm2 driver with docker runtime
Times for minikube start: 52.1s 46.9s 48.0s 49.3s 47.2s Times for minikube ingress: 32.3s 32.8s 31.3s 32.3s 32.8s docker driver with docker runtime
Times for minikube ingress: 27.4s 30.0s 28.5s 26.9s 29.4s Times for minikube start: 22.2s 21.3s 21.9s 21.8s 21.7s docker driver with containerd runtime
Times for minikube start: 31.3s 43.7s 42.8s 24.9s 36.4s |
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
Closes #12546
cri-o hasn't yet implemented the
--force-systemd=true
flag, added the feature.Because cri-o defaults to
systemd
if nocgroup_manager
set in/etc/crio/crio.conf
, I've implemented that passing--force-systemd=true
removescgroup_manager
from/etc/crio/crio.conf
.